For example, the button on the end of the stalk is the KSource button.
It should always be generating codes within the range 0x10 - 0x1c,
preferably 0x16 (mid-range).

If not, then add the config.ini lines shown earlier,
and modify the range to match what the button is really doing.

Cheers

Yeah, I saw that. Part of the problem here is that we have a
guy who has never used a working stalk before, so things will
be very confusing for him. And he may not notice when things
actually work or not.

So, perhaps he could also report here exactly what each button
generates on the display, going through all of the buttons 2-3 times
to get an average.

Cheers

damn... i only have the cable that came with the player

i can do that, in an hour or so, it's dinner time here

I *think* the hole in the bottom rear of the sled makes enough room to use the regular serial port that's built in to the player. Check and see.

not in an peogeot 106. like max 5mm space around the sled

source=0x16
vol+=0x88
vol-=0x71
seek+=0x5c
seek-0x4a
off=0x02
mute=0x2b

and the 3 buttons seen from above with the stalk standing flat on a table.. and the two that side next to each other closeest to you..

single button= 0xb0
left one=0x9b
right one=0x3b

Looks like it is all working normally.

yeah.. i cant get it either. the next problem is serial port trace.. it will take some days before i can do it since i have to route a flat cable from the sled's db9 connector.. only way i can do a trace right now is to get the sled out of the dash

.. or get an ethernet connection into the dash, if that's any easier. The serial port messages could then be retrieved via FTP, I believe.

-ml

no, it's the same trouble.. but i think i can get some connectors and cable by sunday...

is there any further test's i can do?

was there no other chioce than serial or network to do the serial trace? or other test that i can do?

Nothing worthwhile.

ok... so i will aim for a serial port

how should i wire the 2 db9 connectors.. from my pc to the sled connector?

like this?

1+6 ------------ 4 (1 and 6 to 4)
2 -------------- 3 (2 connected to 3)
3 -------------- 2 (3 connected to 2)
4 -------------- 1+6 (4 connected to 1 and 6)
5 -------------- 5 (5 connected to 5)
7 -------------- 8 (7 connected to 8)
8 -------------- 7 (8 connected to 7)

Connect *only* the Tx, Rx, and GND pins (3-wires). Ignore the rest of them.

-ml

ok... but i will report back some time this sunday.... around 20:00 CET i guess

i just soldered a cable... but will the sleds serial work along with the players serial when in the car?

The sled serial port and the serial port on the back of the empeg unit are the same port. One is wired DCE and one is wired DTE.

so if i use the serial on the player while it's docked in the car I just have to cross the wires from pin 2 and 3 ?

just aksing to make sure i dont blow anything up

done the serial trace... but nothing happens in putty when i use the stalk... nor when i use the front panel.. log attached

Okay, add this to the [hijack] section in config.ini, and then get another serial port trace. This time it *will* have stuff in it:

stalk_debug=1

No problem... will be around the same time.. have to "steal" the power at an outdoor outlet...

new log...

and when pressing any button on the stalk the sound is stuttering and ful of clicks...

but strange that the end of the log is just one big space.. but nothing happend on screen

btw.. my config.ini... just to make sure

[Network]
Gateway=192.168.1.1
Netmask=255.255.255.0
IPAddress=192.168.1.11
DHCP=0
[synchronise]
seq_num=41
[wendy]
flag_amount=0
[custom]
wendy=
[searches]
amount=0
[VisualFavourites_AM]
count=0
[VisualFavourites_AUX]
count=0
[VisualFavourites_DSP]
count=0
[VisualFavourites_FM]
count=0
[Options]
Name=Empeg
[controls]
stalk_side=right
[User Info]
Email=
Phone=
Name=Tina Andersen & Bo Herrmannsen
[display]
play_count=1
visual_names=1
caching=1
[kenwood]
disabled=0
[menu]
quit=0
sort_playlist=1
[shuffle]
deduplicate=1
[sense]
muteaction=0
mute=-1
[power]
off_timeout=60000
[hush]
hushpercent=20
[volumecap]
enabled=0
[ramp]
disabled=0
[tuner]
region=europe
[aux]
source=
title=
artist=
[hijack]
stalk_debug=1
decimal_fidentry=1
;@MENUEXEC Set_Date_Time /rdate -s 192.168.1.1 &>/dev/null
temperature_correction=0 ;; default is -4
fan_control=1
fan_low=16
fan_high=21

Your player is doing the "change the baud rate midway through startup"
thing that they do by default when in a car.

Fix it with this, in config.ini, then try again.
This might even fix the stalk, too, now that ya mention it..

[serial]
car_rate=115200 ; Set default rate when on DC to 115kbps

no special place to but this?

i added it just before hijack... now the click/stutter is away... but it's too late to start the car just to drive and do the serial trace...

The stalk itself has not changed

now here it is.. i startede by pressing source.. then vol+,vol-,track+,track-

then the buttons.. off first, the 3 when seen from above and lastly mute...

It still all looks normal.

Code:

Stalk: in=02 01 ff 00 == no button
Stalk: in=02 01 16 17 == 00000031
Stalk: out=02 01 16 17 == 00000031
Stalk: in=02 01 ff 00 == 80000031
..

Can you use the Radio with this player (eg. does the radio work?)?

For some reason, the player software is ignoring the stalk buttons.
This generally happens only if the radio is not detected,
or if the config.ini file says to disable the stalk.

Does this make the button on the end of the stalk work?

[ir_translate]
KSource=Source


??